Xenstore client library spawns a reader thread the first
authorkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Tue, 11 Oct 2005 12:02:59 +0000 (13:02 +0100)
committerkaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk>
Tue, 11 Oct 2005 12:02:59 +0000 (13:02 +0100)
commit490bab7b96c76d645c143e37a4adad5a3f597bbf
tree7526867eadc1ef176ddcbbc7ab939d2fb290a4a1
parent11dde699b056cc7a4941e96449b0bec29fcdc265
Xenstore client library spawns a reader thread the first
time a watch is registered. Before this it is fine for
caller threads to read the comms channel directly as no
async messages will be received.

This avoids various user tools needlessly creating three
threads where one will do the job.

Signed-off-by: Keir Fraser <keir@xensource.com>
tools/xenstore/xs.c